Skip to main content
New

Walkthrough: sharing an app with a group or organization.

You share an app with a group or organization the same way you share with a person: open the Share modal, type the destination, pick a permission, send. This is how partners deploy apps to many districts at once and how org admins distribute curated apps inside their network.

​
When to share with a group or org

Common cases: A Learning Partner wants to give a curated math app to fifteen district partners. Direct share to each org. A district admin wants to make a starter pack of apps available to every school in the district. Share with each school’s org. A curriculum org rolling out a new unit wants every classroom in three networks to have access. Share with each network’s org. For sharing with one specific person, see Sharing with individuals.

​
How to share with a group

1

Open the app or collection

Both apps and Collections share the same way.
2

Click Share

The Share button is in the top right.
3

Type the group name

Start typing. Matching groups inside your org appear as suggestions.
4

Pick a permission level

Pick Viewer to let group members use the app, or Editor for collaborators on the build.
5

Send

Members of the group see the app on their dashboard with the permission you set.

​
How to share with an organization

The flow is the same. In the recipient field, type the organization’s name. If the org is on your partner list or has previously shared with you, it appears in the suggestions. Otherwise, you can type the org’s domain to find it.
The Share modal with a search field for a user, group, or organization, a USERS list with one person and a Select role dropdown, and a GROUPS list showing 'My new group!' set to Viewer, above a Done button.

Sharing with a group or organization is the same flow as sharing with a person: search for it, set a role, then click Done. Here the group 'My new group!' is added as a Viewer.

To share with several orgs at once, add them all to the recipient list. Each org gets its own activity segmentation, so you see usage per org and each org sees only its own.

​
Cross-org sharing

Playlab supports sharing across organizations as a first-class flow. Previously, the only way to deploy an app from one org to another was to remix it. A few things to know about cross-org sharing: The original org owns the app. Updates flow from the source. Recipient orgs see the latest version automatically. Activity is segmented. You see aggregate usage across the orgs you shared with. Each org sees only its own. Permissions cascade. A Viewer permission grants the recipient org’s members the right to use the app. To grant editing rights to specific people in another org, share with them individually as Editors. Recipients can add to their workspaces. Once you share an app with an org, members of that org can add it to their workspaces using the Add Apps flow. For partner-style deployment with curated bundles of apps, Collections are usually a better fit.

​
Activity segmentation

When the same app is in use across several orgs, the data stays separated. You see aggregate stats: how many sessions, how many active users, what conversation topics are common across orgs. Each recipient org sees only its own data. Personally identifiable student information from one org never crosses to another. For more, see Reviewing student activity per class.

​
Key points

  • The same Share modal works for groups and entire organizations
  • Activity stays segmented per recipient org
  • For curated bundles of multiple apps, use Collections instead

​
FAQ

Yes. Add them all to the recipient field. Each gets the same permission level and the app shows up in each org separately.
No. The recipient list is private to you. Each org sees only that you (the source) shared the app with them.
A Viewer-level org share grants every member of that org the right to use the app. Editor-level org sharing is not supported. To grant editing access, share with the specific people who should have it.
The recipient cannot reshare your app outside their org. Inside their org, members can add the app to their workspaces.
Members of that org lose access on their next visit. Conversations they had are preserved in your activity history but no longer visible to them.
Yes. The org-level activity view shows usage by recipient org. You see aggregate stats per org without crossing privacy lines.
Last updated: 06-01-2026 Contact us at [email protected]